6.2.0 Boomi Cloud API Management – Local Edition October 2025 Release Notes

New

We added these features

You can now set up a non-production Boomi Cloud API Management - Local Edition cluster to demonstrate PoCs on your Docker desktops or Docker-enabled desktops and laptops. This cluster uses Minikube as a single-node Kubernetes (K8s) cluster. (EIN-12170)

Refer to the Quickstart Guide for more information.
Added log collector service in Boomi Cloud API Management - Local Edition (Tethered mode), which collects access logs from the Traffic manager and sends them to Cloud API Management (Control Center). (EIN-22160)

Refer to Getting Started with Boomi Cloud API Management - Local Edition for more information.
Updated Helm chart templates and Values.yaml for trafficmanager, platformapi, and configui services to support annotations, labels, and traffic policies.

Refer to 6.2.0 Values.yaml for more information. (EIN-22491)

New

Changes in Boomi Cloud API Management – Local Edition 6.2.0

The following table lists the changes in Boomi Cloud API Management – Local Edition 6.2.0.

6.1.0 (Existing) 6.2.0 (Updated) Description

apimClusterMode tethered The default cluster mode has now been changed to tethered, whereas it was previously untethered. (EIN-22582)

6.1.0 (Existing)	6.2.0 (Updated)	Description
`apimClusterMode`	`tethered`	The default cluster mode has now been changed to tethered, whereas it was previously untethered. (EIN-22582)
`loader.momuri`	`global.mom.uri`	The MOM URI configuration location has been updated from Boomi Cloud API Management – Local Edition 6.1.0 to 6.2.0. Moved from `loader` specific to `global` scope in `Values.yaml` for shared access of loader and log collector (`logsync`). Refer to 6.2.0 Values.yaml for more information. (EIN-22588)
`Values.global.namespace`	`helm install apim deploy --namespace <namespace_name>`	Previously, the namespace parameter had to be specified in 6.1.0 Values.yaml. You can now set it during Helm deployment. (EIN-22198)

loader.momuri

global.mom.uri

The MOM URI configuration location has been updated from Boomi Cloud API Management – Local Edition 6.1.0 to 6.2.0.

Moved from loader specific to global scope in Values.yaml for shared access of loader and log collector (logsync). Refer to 6.2.0 Values.yaml for more information. (EIN-22588)

Values.global.namespace helm install apim deploy --namespace <namespace_name> Previously, the namespace parameter had to be specified in 6.1.0 Values.yaml. You can now set it during Helm deployment. (EIN-22198)

Fix

We fixed these issues

The MySQL database connection count increased after each loader execution. This was because after a job completion, previous connections were not properly closed and returned to the connection pool, causing service disruptions due to exhausted database connections. To fix this issue, we have added standard database connection pool configurations across multiple components by updating the global Values.yaml. (EIN-22314) (EIN-22557)

Refer to 6.2.0 Values.yaml for more information.
After changing the log-level settings for the cache pod, the kubectl logs command still displayed the old log-level configurations instead of the updated ones. This issue has been fixed so that the log levels now reflect the correct configured settings. (EIN-22377)
Cache pod logs experienced frequent SQL errors, which prevented them from connecting to the database. This issue was resolved by adding reconnection capabilities, ensuring reliable data storage. (EIN-22501)
Changing the localDevAdminUser value in the global 6.2.0 (Untethered) Values.yaml caused an issue accessing the Content Management System tab on the Boomi Cloud API Management - Local Edition homepage. This issue is now resolved. (WA-16645)
Previously, deleting an application incorrectly resulted in the deletion of the application’s keys as well as the user’s package keys from other applications. This issue has been resolved. Now, when an application is deleted, only the package keys that are actively associated with it will be removed, and keys from other applications will not be deleted. (WA-16279)
The Mom server proxy configuration was missing earlier in Boomi Cloud API Management - Local Edition 6.1.0. To fix this issue, added proxy configuration for the loader and log collector for connecting to Cloud API Management. (EIN-22305) (EIN-22522) (EIN-22489)
There was an issue when assigning an API key to an application on the Developer Portal. Assigning API keys to applications on the Developer Portal would show an error message. This issue is now resolved. (WA-16675)
Enabling verbose logging for a specific endpoint resulted in an error when capturing Traffic Manager logs. This issue has now been fixed. (EIN-22494)
Previously, the GET call for the SOAP endpoint stopped working when the GET HTTP method setting was disabled on the Endpoint Key & Method detection page. This issue is now resolved. (EIN-22502)
The Kubernetes load balancer changes the source/client IP address when redirecting a call to one of the traffic manager pods. As a workaround, we recommend using the X-Forwarded-For header when making traffic requests. However, it was observed that when the X-Forwarded-For header was missing in the multinode cluster, the V3 access logs showed different source IP addresses. To fix this, set the externalTrafficPolicy value to Local in this file: charts/trafficmanager/values.yaml. (EIN-12217)

Refer to 6.2.0 Values.yaml for more information.
During the rolling upgrade, traffic is disrupted for a few minutes as cache pods are upgraded, and data needs to be loaded in the new cache pods. This issue has been fixed now.

Refer to Upgrading Previous 6.x Versions to 6.1.0 and 6.2.0 (applies to v6.0.0+) for more information. (EIN-12583)

Fix

Known Issues

The following item is a known issue and will be addressed in a future release:

The migration build package filenames for 6.2.0 are incorrectly labeled as 6.1.0 (migrate_4x_to_6_APIM610_9.tar.gz and migrate_5x_to_6_APIM610_65.tar.gz). This will be updated to the 6.2.0 label in the next release. (EIN-22744)